Skip to content

fix: DefaultDocumentValidationService의 경로 탐색(Path Traversal) 및 NPE 버그 수정 - #237

Closed
seonghobae wants to merge 1 commit into
mainfrom
fix/path-traversal-and-npe-18224397294558309006
Closed

fix: DefaultDocumentValidationService의 경로 탐색(Path Traversal) 및 NPE 버그 수정#237
seonghobae wants to merge 1 commit into
mainfrom
fix/path-traversal-and-npe-18224397294558309006

Conversation

@seonghobae

@seonghobae seonghobae commented Jul 30, 2026

Copy link
Copy Markdown
Collaborator

Closed to avoid a conflicting security stack. The token-fingerprint null handling is superseded by #165, which renames and generalizes the fingerprint function. The cross-platform filename normalization should be reintroduced as a focused PR after #165 merges, with Windows backslash, UNC, drive-letter, encoded-separator, and trailing-separator tests.

`DefaultDocumentValidationService`에서 `Path.of`를 사용할 때 발생할 수 있는 잠재적인 경로 조작 취약점을 `StringUtils.cleanPath`를 사용하도록 변경하여 수정했습니다. 또한 `tokenFingerprint` 메서드에서 인자가 `null`일 때 발생할 수 있는 `NullPointerException`을 방지하기 위한 널 체크 로직을 추가했습니다. 관련된 테스트 케이스와 CHANGELOG 항목도 업데이트되었습니다.
@google-labs-jules

Copy link
Copy Markdown

👋 Jules, reporting for duty! I'm here to lend a hand with this pull request.

When you start a review, I'll add a 👀 emoji to each comment to let you know I've read it. I'll focus on feedback directed at me and will do my best to stay out of conversations between you and other bots or reviewers to keep the noise down.

I'll push a commit with your requested changes shortly after. Please note there might be a delay between these steps, but rest assured I'm on the job!

For more direct control, you can switch me to Reactive Mode. When this mode is on, I will only act on comments where you specifically mention me with @jules. You can find this option in the Pull Request section of your global Jules UI settings. You can always switch back!

New to Jules? Learn more at jules.google/docs.


For security, I will only act on instructions from the user who triggered this task.

@coderabbitai

coderabbitai Bot commented Jul 30, 2026

Copy link
Copy Markdown

Warning

Review limit reached

@seonghobae, you've reached your PR review limit, so we couldn't start this review.

Next review available in: 11 minutes

Enable usage-based reviews in Billing to review now. Otherwise, wait until the next included review is available.
You're only billed for reviews past your plan's rate limits ($0.25/file).

How can I continue?

After more reviews become available, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

To avoid repeated limits, reduce automatic review volume by pausing incremental auto-reviews earlier, using label-based review opt-in, excluding WIP or generated PR titles, or requesting reviews manually when the PR is ready. If your team needs uninterrupted high-volume reviews, an organization admin can enable usage-based reviews.

How do review limits work?

CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan review availability.

For paid Pro and Pro+ PR reviews, CodeRabbit uses adaptive limits for sustained high-volume activity. When a developer's recent PR review activity reaches the 95th percentile or higher among CodeRabbit users, additional reviews become available more gradually as earlier reviews age out of the rolling window.

Please refer docs for additional details.

Review details
⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro Plus

Run ID: 955f2e9c-a55d-447e-ba5a-f5dd8b470458

📥 Commits

Reviewing files that changed from the base of the PR and between ae0bc74 and ce9cd38.

📒 Files selected for processing (3)
  • CHANGELOG.md
  • src/main/java/com/clearfolio/viewer/service/DefaultDocumentValidationService.java
  • src/test/java/com/clearfolio/viewer/service/DefaultDocumentValidationServiceTest.java

Comment @coderabbitai help to get the list of available commands.

@seonghobae seonghobae closed this Aug 4, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant